Hey, I implemented a new statement as follows in resourceArmRoleAssignmentCreate, however it doesn't look to wait because the check passes and it gets the ID back, which I kinda expected as it's returning when the creation is down. I think the retry is going to need to be placed on the following:

_, err = roleAssignmentsClient.Create(ctx, scope, name, properties)

Here is my hack about so far which is similar to @joakimhellum-in has committed so far:

	err :=  resource.Retry(120*time.Second, validatePrincipalIdExists(principalId, meta))
	if err != nil {
		return err
	}

func validatePrincipalIdExists(principalId string, meta interface{}) func() *resource.RetryError {
	
	return func() *resource.RetryError {
		servicePrincipalsClient := meta.(*ArmClient).servicePrincipalsClient
		ctx := meta.(*ArmClient).StopContext
		
		_, err := servicePrincipalsClient.Get(ctx, principalId)

		if err != nil {
			return resource.RetryableError(err)
		}
		return nil
		
	}
}

I submitted PR #1647 with a tested solution.

thanks alot. i will close this one in favor of #1647
@mb290 @tombuildsstuff FYI did create some hundred service principals past week and found that 2 minutes might be enough (as opposed to 3min). not sure if you got the same results.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!